home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
gt_power
/
histbeta.zip
/
HISTORY.DOC
< prev
next >
Wrap
Text File
|
1988-10-14
|
13KB
|
398 lines
GENHIST/PLAYHIST: v2.01 by Stephen de Plater
October 14, 1988 GT Net Address 36/1
GENHIST / PLAYHIST
by Stephen de Plater
GT Net Address: 36/1
Phone: +61 2 977-3075
======================================================================
0. REVISION LIST
======================================================================
Just to confuse everyone this revision list begins at version 1.10
VERSION: Release Date: Comments:
------- ------------ --------------------------------------
1.10 May 26, 1988 These two programs replace (at least
for users of GT1400) the older program
HISTORY.EXE
Added Standard Command Line Interface.
1.11 August 12, 1988 Fixed a couple of minor bugs and added
the new /B parameter.
2.00 October 12, 1988 As you might guess, a major revision!
In fact, the code changes were quite
small, but ... External protocol file
transfers are now counted (they never
were before), people who like to wierd
things in their GT.CNF are
accomodated, and the different format
of the GT14.03 log is handled.
2.01 October 14, 1988 A very small change to accomodate
those who put their GT.LOG files in
directories other than the GTPATH.
>> page 1 <<
GENHIST/PLAYHIST: v2.01 by Stephen de Plater
October 14, 1988 GT Net Address 36/1
======================================================================
1. COPYRIGHT
======================================================================
GENHIST / PLAYHIST are not placed in the Public Domain. The copyright
is retained and the software is provided on licence:
You are free to use and make as many copies of these programs as you
wish. You may also give them away to anyone who wants it, provided:
1. No fee is charged.
2. This archive is distributed intact.
3. You register the package with me.
======================================================================
2. REGISTRATION
======================================================================
Registration is simple. There is no fee involved at all. DO NOT send
any money! Registration simply involves sending a me a postcard
advising that you are using the program. That way I can let you know
about updates etc. (It also helps my ego to know that there are people
who use my stuff!)
Send the card to: Rev. Stephen de Plater
1 Kangaroo St.
MANLY, NSW, 2095
Australia
======================================================================
3. PURPOSE
======================================================================
(Or what does this thing do anyway?)
GENHIST / PLAYHIST together form a door program for GT Power BBS
Systems. In combination they present to users some of the usage
statistics for the previous day.
Specifically, GENHIST (run once only per day as soon as possible after
midnight -- 24:01 would be good time!) generates the two files
containng the statistical presentation, and
>> page 2 <<
GENHIST/PLAYHIST: v2.01 by Stephen de Plater
October 14, 1988 GT Net Address 36/1
PLAYHIST, a door program, displays the appropriate one of those files
to the user. If you wish to insist that your users see this
information (as some systems in Sydney do) then you should include
PLAYHIST in your logon door. If you are not running GT1400 and
therefore do not have logon doors available, then with a bit of
judicious DOS copying you could add the output to your logon bulletin.
The output includes:
1. The number of users known to the system,
2. The number of users currently banned,
3. The number of known users who were online yesterday,
4. The number of connects registered yesterday. It may be quite
different from 3 above, if for instance, some users logged on a
number of times.
5. The total, minimum, maximum, and average time used in minutes
and seconds,
6. The total, minimum, maximum, and average number of bytes
downloaded from your system,
7. The total, minimum, maximum, and average number of bytes
uploaded to your system.
The output will be presented in a standard form which is always 14
lines long, including blank top and bottom lines.
>> page 3 <<
GENHIST/PLAYHIST: v2.01 by Stephen de Plater
October 14, 1988 GT Net Address 36/1
======================================================================
4. USAGE
======================================================================
To use the GENHIST / PLAYHIST combination:
1. Place both programs in your DOS path.
2. Create a scheduled event which will run GENHIST immediately
after midnight.
3. Add PLAYHIST to your logon door.
======================================================================
5. COMMAND LINE PARAMETERS
======================================================================
GENHIST supports three command line parameters as follows:
1. /Dnn Delay time in seconds. If this is the only program in your
midnight event, then it will run very quickly, and you
will be returned to the bbs before the minimum window for
the event (one minute) has elapsed. If that occurs you
will immediately go out and run the event again, and
again, and again ... until the minute is used up. To
prevent this happening, this parameter forces GENHIST to
take at least nn seconds to complete.
The default time is 60 seconds.
2. /N By default, GENHIST will create (and PLAYHIST will look
for) files called HISTORY.BBS and HISTORY.CBS. If you want
a different name, this is where you put it. You may only
supply the simple filename here, NOT the extension, which
will be added by GENHIST. You should not specify a path--
GENHIST and PLAYHIST will always look only in the GTPATH
directory for these files.
For example, if you want to use the name "MYHIST" instead
of "HISTORY" and have GENHIST create MYHIST.BBS and
MYHIST.CBS, then use the following parameter:
/Nmyhist
>> page 4 <<
GENHIST/PLAYHIST: v2.01 by Stephen de Plater
October 14, 1988 GT Net Address 36/1
Note that there are NO spaces allowed!
3. /B If the /B parameter is supplied it must be followed
immediately by one single (case sensitive) character. This
character represents one access level which is treated as
a ban level. Some sysops do not wish to simply ban
unwanted users, because that prevents the log recording
any attempts by them to get on, but instead set up a level
with a very short time and no effective access which has
the same effect. On this system, for instance, it is level
"z". Be careful of the case (it does count), and note that
for this to register this way it must be an exact match.
i.e: /Bx would only ban users at level "x", but not at
levels "y" or "z". On this system I use /Bz.
The command line parameters may not be run together, and may not
contain internal spaces. i.e.: "/d 99", "/d99/nMYHIST" are both wrong;
"/d99 /nMYHIST" is fine! Case does not matter.
PLAYHIST supports two command line parameters as follows:
1. /M Force ANSI graphics OFF, no matter whether the user has
them selected or not. The default is to let users who have
selected ANSI graphics see the color file, and users who
have not see the monochrome file.
2. /N Use a different filename other than HISTORY.BBS and
HISTORY.CBS. Matches the same parameter in GENHIST.
======================================================================
6. COLORS
======================================================================
PLAYHIST is sensitive to the presence of GT1400. If it is detected,
and if the user has ANSI graphics selected, CHANGE will use the colors
which the GT1400 is using. Otherwise, it will run in monochrome. There
is nothing which you have to do to tell it which version you are
running -- let it figure it out for itself!
GENHIST makes no assumptions. It creates files for both color and
monochrome.
>> page 5 <<
GENHIST/PLAYHIST: v2.01 by Stephen de Plater
October 14, 1988 GT Net Address 36/1
======================================================================
7. DISCLAIMER
======================================================================
Q: What kind of guarantee comes with this software?
A: *** ABSOLUTELY NONE!!! ***
I take no responsibility at all for what this software may do on any
computer other than my own. If you use it you do so at your own risk.
All that I am prepared to say about it is that it works fine here (and
I can see no good reason why it should not also work fine everywhere
else also -- but ....)
By using this program you accept these conditions.
======================================================================
8. ENJOY!
======================================================================
At least, I hope you do!
Stephen
>> page 6 <<